Add manifest boundary fixture validation#1
Closed
Yehonal wants to merge 1 commit into
Closed
Conversation
Contributor
Author
|
Closing intentionally after review: the manifest/boundary taxonomy is too private/domain-specific for the public agent-mesh repo. We will keep agent-mesh focused on OSS mesh protocol/transports/generic safety and move private manifest/domain/role boundary work to the private toolkit/docs. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
packages/coreboundary_class+pathwithout echoing private valuesmanifest:fixturesinto the rootnpm run verifygateBoundary classes covered
core-neutralsensitive-business-domain-boundaryclient-project-boundaryprivate-assistant-boundarydevelopment-agent-boundarystaff-community-boundaryTest plan
npm run verifyNotes
This PR intentionally keeps real domain/bot/role topology out of the public repo. The private domain/role/agent manifest planning remains in the private OpenClaw/shared docs and should be handled separately after this review.